Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.8] bpo-38708: email: Fix a potential IndexError when parsing Message-ID (GH-17504) #17515

Merged
merged 1 commit into from Dec 9, 2019

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Dec 9, 2019

Fix a potential IndexError when passing an empty value to the message-id
parser. Instead, HeaderParseError should be raised.
(cherry picked from commit 3ae4ea1)

Co-authored-by: Abhilash Raj maxking@users.noreply.github.com

https://bugs.python.org/issue38708

…ythonGH-17504)

Fix a potential IndexError when passing an empty value to the message-id
parser. Instead, HeaderParseError should be raised.
(cherry picked from commit 3ae4ea1)

Co-authored-by: Abhilash Raj <maxking@users.noreply.github.com>
@miss-islington
Copy link
Contributor Author

@maxking: Status check is done, and it's a success ✅ .

@miss-islington miss-islington merged commit 2abd3a8 into python:3.8 Dec 9, 2019
@miss-islington miss-islington deleted the backport-3ae4ea1-3.8 branch December 9, 2019 02:12
@miss-islington
Copy link
Contributor Author

@maxking: Status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
Contributor Author

@maxking: Status check is done, and it's a success ✅ .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants